System and method of testing using test pattern re-execution in varying timing scenarios for processor design verification and validation

ABSTRACT

A system and method processor testing using test pattern re-execution is presented. A processor re-executes test patterns using different timing scenarios in order to reduce test pattern build time and increase system test coverage. The invention described herein varies initial states of a processor&#39;s memory (cache, TLB, SLB, etc.) that, in turn, varies the timing scenarios when re-executing test patterns. By re-executing the test patterns instead of rebuilding new test patterns, verification quality is improved since more time is available for execution, verification and validation. In addition, since the test patterns result in the same final state, the invention described herein also simplifies error checking.

BACKGROUND OF THE INVENTION

1. Technical Field

The present invention relates to a system and method for re-executingtest patterns in varying timing scenarios for processor design andverification. More particularly, the present invention relates to asystem and method of re-executing test patterns at different initialcache line memory states, which creates different timing scenarios whenthe processor executes the test patterns.

2. Description of the Related Art

A processor test team typically employs test patterns in order to verifyand validate a system design. Processor testing tools exist whose goalis to generate the most stressful test pattern for a processor. Intheory, the generated test pattern should provide maximum test coverageand should be interesting enough to stress various timing scenarios onthe processor. The whole technology of these tools sits in the logic ofbuilding these test patterns.

Verifying and validating a processor using test patterns typicallyincludes three stages, which are 1) test pattern build stage, 2) testpattern execution stage, and 3) validation and verification stage. Achallenge found is that the test pattern build stage is typically themost time consuming process in any verification process, whichovershadows the actual time spent on test pattern execution. As aresult, little time is left for test pattern execution andvalidation/verification stages.

What is needed, therefore, is a system and method that reduces testpattern build times in order to allocate more time for test patternexecution and validation/verification stages.

SUMMARY

It has been discovered that the aforementioned challenges are resolvedusing a system and method of re-executing test patterns using differenttiming scenarios in order to reduce test pattern build time and increasesystem test coverage. The invention described herein varies initialstates of a processor's memory that, in turn, varies the timingscenarios when re-executing test patterns. By re-executing the testpatterns instead of rebuilding new test patterns, verification qualityis improved since more time is available for execution, verification andvalidation. In addition, since the test patterns result in the samefinal state, the invention described herein also simplifies errorchecking.

When a test pattern includes load-store instructions, the load-storeinstructions, when executed for the first time, fetch data from memory.During the next test pattern re-execution, however, some of the data maystill reside in cache depending upon the cache implementation. Forexample, two test patterns may have load instructions to differentmemory locations that are mapped to the same cache entry, which resultsin an unpredictable cache hit/miss. In this example, the cache entryincludes data corresponding to the test pattern that executed last.

In a multi-processor scenario, load and store instructions may be builtusing “false” sharing logic in which the processors do not share thesame target memory address, but may share the same cache line in thecache. Thus, a test pattern with the same initial state may take adifferent course en route to completion or execute under a new processorstate during subsequent re-executions of the same test pattern. However,since the same test pattern results in the same final state of thememory and processor registers, error-checking mechanisms aresimplified, which also reduces verification/validation time.

The foregoing is a summary and thus contains, by necessity,simplifications, generalizations, and omissions of detail; consequently,those skilled in the art will appreciate that the summary isillustrative only and is not intended to be in any way limiting. Otheraspects, inventive features, and advantages of the present invention, asdefined solely by the claims, will become apparent in the non-limitingdetailed description set forth below.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention may be better understood, and its numerousobjects, features, and advantages made apparent to those skilled in theart by referencing the accompanying drawings.

FIG. 1 is a diagram showing a multi-processor system using an onboardgenerator/tester for processor design verification and validation;

FIG. 2 is a diagram showing a generator/tester generating test patternsand comparing hardware results against simulation results duringprocessor design verification and validation;

FIG. 3 is a diagram showing a test pattern generator generating testpatterns based upon architectural rules and initialization information;

FIG. 4A is a diagram showing a general operating system execution modethat comprises a user mode and a kernel mode;

FIG. 4B is a diagram showing an innovative operating system executionmode;

FIG. 5 is a diagram showing a test pattern generator using a testpattern simulator to execute test patterns and compute simulation errordetection check values, which are subsequently passed to a test patternexecutor that performs error detection checks using the simulation errordetection check values and hardware error detection check values;

FIG. 6 is a diagram showing a test pattern generator providing “n” testpatterns to a plurality of test pattern executors in order to increaseoverall test time throughput;

FIG. 7 is a flowchart showing steps taken in re-executing test patternsin varying timing scenarios;

FIG. 8 is a diagram showing a test pattern generator generating testpatterns that, when executed, provides interesting test scenarios bysharing page table memory for test pattern memory;

FIG. 9 is a flowchart showing steps taken in re-executing test patternsin varying timing scenarios;

FIG. 10 is a diagram showing an L2 cache's initial state prior to a testpattern execution;

FIG. 11 is a diagram showing an L2 cache's state after executing testpatterns on a plurality of processors a first round;

FIG. 12 is a diagram showing an L2 cache's state after executing testpatterns on a plurality of processors a second round;

FIG. 13 is a diagram showing cache snoop logic and coherencyverification between an instruction cache (icache) and a data cache(dcache);

FIG. 14 is a diagram showing a processor executing multiple testpatterns on multiple threads to quickly test each entry in a translationlookaside buffer (TLB);

FIG. 15 is a diagram showing a processor executing multiple testpatterns on multiple threads to fully test an L2 cache;

FIG. 16 is a flowchart showing steps taken in testing an entire TLBmemory;

FIG. 17 is a flowchart showing steps taken in providing full testcoverage of a cache;

FIG. 18 is a flowchart showing steps taken in generating test patternsto test lwarx and stwcx instructions;

FIG. 19 is a diagram showing test pattern execution that includes pairedlwarx-stwcx instructions in a non-interrupt mode;

FIG. 20 is a table showing different test pattern execution scenariosthat result in different bus contention scenarios;

FIG. 21 is a diagram showing two processors executing two different testpatterns, which results in a particular bus timing scenario anddifferent states of functional units during execution;

FIG. 22 is a diagram showing a broadband element architecture whichincludes a plurality of heterogeneous processors capable of implementingthe invention described herein;

FIG. 23 is a block diagram illustrating a processing element having amain processor and a plurality of secondary processors sharing a systemmemory; and

FIG. 24 illustrates a simplified example of a computer system capable ofperforming the computing operations described herein.

DETAILED DESCRIPTION

The following is intended to provide a detailed description of anexample of the invention and should not be taken to be limiting of theinvention itself. Rather, any number of variations may fall within thescope of the invention, which is defined in the claims following thedescription.

FIG. 1 is a diagram showing a multi-processor system using an onboardgenerator/tester for processor design verification and validation.Multi-processor system 100 includes processor A 110, processor B 120,processor C 130, and processor D 140. As one skilled in art canappreciate, more or less processors may be used in a multi-processorsystem other than the example shown in FIG. 1 for processor designverification and validation.

Processor A 110 includes generator/tester 150, which generatespseudo-random test patterns that are distributed to each processor.Generator/tester 150 receives input from user interface 155 andretrieves architectural rules from architectural details 160 in order togenerate the pseudo-random test patterns (e.g., test pattern A 165, testpattern B 170, test pattern C 175, and test pattern D 180). Thepseudo-random test patterns fully test multi-processor 100's memory andtiming characteristics based upon the retrieved architectural rules.Architectural details 160 may be stored on a nonvolatile storage area,such as a computer hard drive.

After the processor executes the test patterns, generator/tester 150receives hardware results (e.g., results B 185, results C 190, andresults D 195) from the processors and compares the results againstsimulation results in order to ensure that multi-processor system 100operates in a manner consistent with the architectural rules (see FIG. 2and corresponding text for further details regarding generator/tester150).

FIG. 2 is a diagram showing a generator/tester generating test patternsand comparing hardware results against simulation results duringprocessor design verification and validation. Generator/tester 150includes initializer 200, test pattern generator 210, simulator 220,test pattern executor 230, and results comparator 250. User interface155 provides user input to initializer 200 and test pattern generator210, such as instruction types to execute, memory range, the number ofinstructions to build in a test pattern, etc. In turn, initializer 200provides initialization information to test pattern generator 210.Generator/tester 150 and user interface 155 are the same as that shownin FIG. 1.

Test pattern generator 210 uses the initialization information, alongwith architectural rules from architectural details 160, to generatepseudo-random test patterns for a plurality of processors. Test patterngenerator 210 provides the test patterns to simulator 220 and testpattern executor 230. Test pattern executor 230 dispatches the testpatterns to processors 240 that, in turn, execute the test patterns.Processors 240 then provide hardware results back to test patternexecutor 230. Architectural details 160 is the same as that shown inFIG. 1.

Test pattern executor 230 provides the hardware results to resultscomparator 250, which compares the hardware results with simulationresults generated by simulator 220. Results comparator 250 then informstest pattern executor 230 as to whether the hardware results match thesimulation results. In turn, test pattern executor 230 dispatches moretest patterns to processor 240 accordingly. In one embodiment, testpattern executor 230 resides on processors 240 (see FIG. 3 andcorresponding text for further details). In another embodiment, resultscomparator 250 resides within test pattern executor 230 (see FIG. 5 andcorresponding text for further details). In these embodiments, thefunctions that test pattern executor 230 and results comparator 250perform are similar to their functions described above.

FIG. 3 is a diagram showing a test pattern generator generating testpatterns based upon architectural rules and initialization information.Initializer 200 provides initialization information to test patterngenerator 210, which stores the initialization information ininstruction pool table 310, register pool manager 320, and memorymanager 330. Instruction pool table 310 includes information such as atable of different instruction classes such as VMX instructions,floating point instructions, fixed point instructions, load/storeinstructions, etc. Register pool manager 320 includes tables such asgeneral purpose registers (GPR), special purpose registers (SPR),hardware implementation registers (HID), etc. And, memory manager 330includes memory pages described by hash tables, page data structures,allocation rules, etc. Test pattern engine 300 uses the initializationinformation, along with architectural rules 340 retrieved fromarchitectural details 160, to generate pseudo-random test patterns thatare provided to processors 240. Architectural details 160, initializer200, and test pattern generator 210 are the same as that shown in FIG.2.

FIG. 4A is a diagram showing a general operating system execution modethat comprises a user mode and a kernel mode. When an operating systemperforms design verification and validation tasks, test patterngenerator 400 and a portion of test pattern executor 410 (scheduler 420and comparator 430) function in the user mode, while the remainingportion of test pattern executor 410 (dispatcher 440) functions in thekernel mode to dispatch test patterns. This results in longer test timedue to the context switch required from user mode to kernel mode.

FIG. 4B is a diagram showing an innovative operating system executionmode. FIG. 4B is different than FIG. 4A in that each module within testpattern executor 410 (scheduler 420, comparator 430, and dispatcher 440)operates in the kernel mode, while test pattern generator 400 operatesin the user mode. By performing design verification and validation usingthe mode shown in FIG. 4B, the invention described herein avoids contextswitching between user mode and kernel mode, thus reducing overall testtime.

FIG. 5 is a diagram showing a test pattern generator using a testpattern simulator to execute test patterns and compute simulation errordetection check values, such as a cyclic redundancy check (CRC), whichare subsequently passed to a test pattern executor that performs errordetection checks using the simulation error detection check values andhardware error detection check values. The configuration shown in FIG. 5may be used in various embodiments, some of which are described below.

In a first embodiment, test pattern generator 500 generates one testpattern for executing a particular number of times on a processor. Inthis embodiment, test pattern generator 500 provides the test pattern totest pattern simulator 510 that, in turn, simulates the test pattern andreturns simulation results (simulation error detection check values,such as CRC values) to test pattern generator 500. Test patterngenerator 500 then provides the test pattern, along with the simulationerror detection check values, to test pattern executor 520, whichprovides them to scheduler 530. Scheduler 530 schedules the test patternto dispatcher 540, which dispatches the test pattern to processor 550.

Continuing with the first embodiment, processor 550 executes the testpattern and provides hardware results to results comparator 570, such asa CRC comparator. Scheduler 530 instructs results comparator 570 tocompute hardware error detection check values using the hardwareresults, and perform an error detection check by comparing the hardwareerror detection check values against the simulation error detectioncheck values. In turn, results comparator 570 provides a pass/failindication to scheduler 530. If the comparison passes, test patternexecutor 520 may re-execute the same test pattern again to ensure thatthe same hardware error detection check values are computed. As aresult, since the test patterns themselves are not changed, overall testtime is significantly reduced.

In a second embodiment, test pattern generator 500 generates a set of“n” test patterns per processor for executing a particular number oftimes on a plurality of processors (see FIGS. 6, 7, and correspondingtext for further details). In this embodiment, test pattern generator500 provides the test patterns, for processor 550, to test patternsimulator 510 that, in turn, simulates the test patterns and returnssimulation results (simulation error detection check values) to testpattern generator 500. In turn, test pattern generator 500 provides thetest patterns, along with the simulation results, to test patternexecutor 520, which provides them to scheduler 530. Scheduler 530schedules one of the test patterns to dispatcher 540, which dispatchesthe test pattern to processor 550.

Continuing with the second embodiment, processor 550 executes the testpattern and provides hardware results to results comparator 570.Scheduler 530 instructs error detection check comparator 570 to computea hardware register error detection check value using the hardwareresults, and perform a register error detection check by comparing thehardware register error detection check value against the simulationregister error detection check value. If the comparison passes, testpattern executor 520 determines whether each test pattern included inthe set of test patterns has been executed. If not, scheduler 530selects a different test pattern from the set of test patterns and sendsthe test pattern to dispatcher 540 to dispatch. Once all of the testpatterns have been executed at least once, scheduler 530 instructionsresults comparator 570 to compare a hardware memory error detectioncheck value against a simulation memory error detection check value. Asa result, since a memory error detection check is not performed aftereach test pattern execution, but rather after all test patterns haveexecuted, less time is spent performing error detection checks, whichallows more time to execute test patterns.

In a third embodiment, test pattern generator 500 generates a testpattern that is independent of initial data values. In this embodiment,test pattern generator 500 provides the test pattern, along with aninitial set of data values, to test pattern simulator 510. Test patternsimulator 500 simulates the test pattern and produces a simulationresult (simulation error detection check values). Test pattern simulator510 then uses the simulation results as input values for a second testpattern execution round. Test pattern simulator 510 continues tosimulate the test pattern and use the test pattern's simulation resultsas input data values for a next simulation for a particular number oftimes. Finally, test pattern simulator 510 provides the simulationresults of all successive simulations to test pattern generator 500.

Continuing with this embodiment, once test pattern simulator 510 hassimulated the test pattern a particular number of times, test patterngenerator 500 passes the test pattern, the initial data values, and thesimulation results to test pattern executor. Test pattern executor 520uses scheduler 530 and dispatcher 540 as discussed above to schedule anddispatch the test pattern to processor 550. Processor 550 executes thetest pattern and provides hardware results to results comparator 570,which computes hardware error detection check values and compares themagainst the simulation error detection check values. If they match,scheduler 530 and dispatcher 540 dispatch the same test pattern alongwith the hardware results of previous executions to be used as initialdata values (similar to test pattern simulator 510 above). Eachexecution round has a separate simulation error detection check value.This continues for the same number of times that test pattern simulator510 re-executed the test pattern. As a result, since the same testpattern is used, less time is spent on generating test patterns, whichallows more time to execute the test patterns.

In the third embodiment test pattern generator 500 ensures that the testpatterns include known and predictable values since a test pattern mayproduce unknown values through various means. Test pattern generator 500aborts those instructions that generate architecturally unknown results.For example, floating point arithmetic instructions may set registercontents as infinity or NAN (not a number) after a few registeroperations. In addition, test pattern generator 500 generates testpatterns in a manner such that test pattern executor 520 is not requiredto change translations for every test pattern execution. For example,when executing a test pattern using different initial values, realaddress and offsets may change in real mode, which requires a change intranslation. However, test pattern generator 500 avoids the translationchange by ensuring that the same page/address is targeted in real mode.

FIG. 6 is a diagram showing a test pattern generator providing “n” testpatterns to a plurality of test pattern executors (each executing onseparate processors) in order to increase overall test time throughput.Test pattern generator 600 provides test pattern 0A 610, test pattern 1A615, test pattern 2A 620, and test pattern 3A 625 to test patternexecutor 630 and test pattern 0B 611, test pattern 1B 616, test pattern2B 621, and test pattern 3B 626 to test pattern executor 640. In turn,test pattern executor 630 dispatches the test patterns to processor A650 and test pattern executor 640 dispatches the test patterns toprocessor B 660. During execution, processor A 650 and processor B 660may communicate with each other, or retrieve information from mainmemory 680, through bus 670.

After each test pattern execution, test pattern executor 630 and testpattern executor 640 perform a register error detection check. Forexample, after processor A 650 executes test pattern 0A and processor B660 executes test pattern 0B, test pattern executor 630 and test patternexecutor 640 both compute a hardware register error detection checkvalue based upon hardware results from their respective processors, andmatch the computed values against simulation register error detectioncheck values (see FIG. 7 and corresponding text for further details).

Once processor A 650 finishes executing all of its corresponding testpatterns at least once, and processor B 660 finishes executing all ofits corresponding test patterns, test pattern executor 630 and 640 eachperforms a memory error detection check comparison against simulationvalues, and sets an error flag if the comparison values do not match(see FIG. 7 and corresponding text for further details). By waitinguntil all of the test patterns execute before performing a memory errordetection check, verification time decreases, which increases the amountof time available for test pattern execution and, therefore, increasestest coverage.

FIG. 7 is a flowchart showing steps taken in re-executing test patternsin varying timing scenarios. Processing executes a set of test patternsfor each processor and waits until each test pattern included in the setof test patterns has executed before performing a memory error detectioncheck. For example, a system may include test pattern set A and testpattern set B, which execute on processor A and processor B,respectively. In this example, each of the test pattern sets includes anumber of test patterns, such as ten test patterns. Continuing with thisexample, processing waits until all ten test patterns included in testpattern set A have executed at least once on processor A, and all tentest patterns included in test pattern set B have executed at least onceon processor B before performing a memory error detection check. As aresult, less time is spent on memory error detection checks, whichallows more time to execute test patterns (see FIG. 6 and correspondingtext for further details). In one embodiment, processing may perform amemory error detection check after “X” executions given the conditionthat each test pattern has executed at least once.

Processing commences at 700, whereupon processing builds logic andcomputes simulation error detection check values based upon simulationresults, such as simulation register error detection check values andsimulation memory error detection check values (step 710). For example,the simulation error detection check values may be computed using acyclic redundancy check (CRC). At step 720, processing selects a testpattern from a corresponding test pattern set to be executed on eachprocessor (test pattern 0A for processor A and test pattern 0B forprocessor B). Processors 725 execute the selected test patterns, andprocessing saves the execution results at step 730.

Next, processing computes a hardware register error detection checkvalue (e.g., CRC value) for each of processors 725 based upon theirexecution results (step 740), and a determination is made as to whetherthe hardware register error detection check values equal the simulationregister error detection check values (decision 750). If the hardwareregister error detection check values do not equal the simulationregister error detection check values, decision 750 branches to “No”branch 752 whereupon processing sets a global error flag (step 755) andends at 760.

On the other hand, if the hardware register error detection check valuesequal the simulation register error detection check values, decision 750branches to “Yes” branch 758 whereupon a determination is made as towhether all of the test patterns included in each test pattern set haveexecuted at least once on their respective processors (decision 765). Ifall of the test patterns have not executed at least once, decision 765branches to “No” branch 767, which loops back to select another testpattern. This looping continues until all test patterns included in eachtest pattern set have executed at least once on their respectiveprocessors, at which point decision 765 branches to “Yes” branch 769whereupon processing computes a hardware memory error detection checkvalue (e.g. CRC value) at step 770.

A determination is made as to whether the hardware memory errordetection check value matches the simulation memory detection checkvalue (decision 780). If the hardware memory error detection check valuedoes not match the simulation memory detection check value, decision 780branches to “No” branch 782 whereupon processing sets a global errorflag at step 755, and ends at 760. On the other hand, if the hardwarememory error detection check value matches the simulation memorydetection check value, decision 780 branches to “Yes” branch 788.

A determination is made as to whether to continue processor verificationat decision 790. For example, system verification may require each testpattern set to execute 100 times on its respective processor. Ifprocessor verification is to continue, decision 790 branches to “Yes”branch 792, which loops back to step 720, whereupon a test pattern fromeach of the test pattern sets is selected to execute on its respectiveprocessor. This looping continues until processor verification shouldterminate, at which point decision 790 branches to “No” branch 798whereupon processing ends at 799.

FIG. 8 is a diagram showing a test pattern generator generating testpatterns that, when executed, provide interesting test scenarios bysharing page table memory for test pattern memory (e.g., instruction anddata). A processor comprises sub units such as a cache, a TLB(translation look aside buffer), an SLB (segment look aside buffer), anMMU (memory management unit), etc. As such, Test pattern generator 800generates test patterns in order to utilize memory in manner that ismost effective for testing each of the sub units.

In addition to instruction memory, data memory is also shared acrossprocessors and test patterns. Since a processor's architectural rulesmay not specify that page table memory is restricted to only translationpurposes, the test patterns are generated in order to test conditionswhen the page table memory is used for purposes other than translation.

Test pattern generator 800 generates test pattern 0 805 and test pattern1 810, which are provided to test pattern executor 815 and test patternexecutor 820, respectively. In turn, test pattern executor 815 and testpattern executor 820 dispatch the test patterns to processor A 825 andprocessor B 840, respectively. Test pattern 0 805 and test pattern 1 810are generated such that their memory is pseudo-randomly allocated. As aresult, the memory is distributed across processors and across multipletest patterns (in a case of N test patterns per processor).

When processor A 825 executes test pattern 0 805, instruction cache 830includes “ADDR 3” and data cache 835 includes “ADDR 0” and “ADDR 1.”Similarly, when processor B 840 executes test pattern 1 810, instructioncache 845 includes “ADDR 3” and data cache 850 includes “ADDR 0” and“ADDR 2.”

As such, as can be seen in L2 cache 860, cache line 0 862 includesinformation pertaining to test pattern 0 805 as well as test pattern 1810, which is pulled from address 0 882 in main memory 880 over bus 870.Cache line 1 864 includes page table entry information that is pulledfrom address 1 884 in main memory 880. Cache line 2 866 includesinformation pertaining to test pattern 0 805 as well as test pattern 1810, which is pulled from address 2 888 in main memory 880. And, cacheline 3 868 includes information pertaining to test pattern 0 805 as wellas test pattern 1 810, which is pulled from address 3 886 in main memory880.

On many occasions, when a test pattern is generated, a page table is notfully utilized. In such cases, the test patterns utilize the unusedmemory as DATA or instruction memory. As such, when the test patternexecutes, an MMU may be updating the Page Table Entry (PTE) lines incache at the same time another processor is updating the data memory inthe same page that the PTE entry resides or accesses instruction memory.

FIG. 9 is a flowchart showing steps taken in re-executing test patternsin varying timing scenarios. The invention described herein verifies aprocessor by re-executing the same test pattern that results in the samefinal memory and register states in spite of different timing scenariosunder which the execution occurs (see FIGS. 10-12 and corresponding textfor further details).

Processing commences at 900, whereupon processing builds logic andcomputes simulation error detection check values based upon simulationresults, such as simulation register error detection check values andsimulation memory error detection check values (step 910). For example,the simulation error detection check values may be computed using acyclic redundancy check (CRC). At step 920, processing executes a testpattern on each of processors 925 (different test pattern for eachprocessor). Processing stores execution results from each of processors925 at step 930.

Next, processing computes a hardware register error detection checkvalue (e.g., CRC value) for each of processor 925 based upon theirexecution results (step 940), and a determination is made as to whetherthe hardware register error detection check values equal the simulationregister error detection check values (decision 950). If the hardwareregister error detection check values do not equal the simulationregister error detection check values, decision 950 branches to “No”branch 952 whereupon processing sets a global error flag (step 955) andends at 960.

On the other hand, if the hardware register error detection check valuesequal the simulation register error detection check values, decision 950branches to “Yes” branch 958 whereupon processing computes a hardwarememory error detection check value (e.g. CRC value) at step 970.

A determination is made as to whether the hardware memory errordetection check value matches the simulation memory detection checkvalue (decision 980). If the hardware memory error detection check valuedoes not match the simulation memory detection check value, decision 980branches to “No” branch 982 whereupon processing sets a global errorflag at step 955, and ends at 960. On the other hand, if the hardwarememory error detection check value matches the simulation memorydetection check value, decision 980 branches to “Yes” branch 988.

A determination is made as to whether to continue processor verificationat decision 790. For example, system verification may require each testpattern to execute 100 times on its respective processor. If processorverification is to continue, decision 990 branches to “Yes” branch 992,which loops back to 920, whereupon a test pattern from each of the testpattern sets is selected to execute on its respective processor. Thislooping continues until processor verification should terminate, atwhich point decision 990 branches to “No” branch 998 whereuponprocessing ends at 999.

FIG. 10 is a diagram showing an L2 cache's initial state prior to a testpattern execution. When a processor executes load-store instructionsfrom a test pattern for a first time, the processor fetches the datafrom main memory. During the next re-execution, however, some data mayalready reside in cache depending upon the cache implementation. Thisprovides different timing scenarios when a processor re-executes thesame test pattern.

In a multi-processor scenario, a test pattern can be constructed usingfalse sharing logic in which the processors do not share the same targetmemory address, but where the processors share the same cache lines inthe cache. Thus, a test pattern with the same initial state may take adifferent course en route to completion or produce a different processorstate under subsequent re-executions of the same test pattern. Even so,the processor memory and registers still result in the same final state(see FIGS. 11-12 and corresponding text for further details).

Test pattern generator 1000 generates test patterns 0 1010 and testpattern 1 1015, which are provided to test pattern executors 1020 and1025, respectively. In turn, test pattern executor 1020 dispatches testpattern 0 1010 to processor A 1030, which executes the test patternusing thread A. And, test pattern executor 1025 dispatches test pattern1 1015 to processor B 1035, which executes the test pattern using threadB. In one embodiment, a processor may not have threads, or one processormay have multiple threads. In this embodiment, each thread executes onetest pattern.

Both threads use L2 cache 1040 as they transfer information to/from mainmemory 1060 through bus 1050 during test pattern execution. Main memory1060 comprises lines X1 1062 through X4 1070 and Y1 1068 through Y31074, which include instruction and data information. Depending upontiming conditions, L2 cache 1040 will still include informationpertaining to test pattern 0 1010 and test pattern 1 1015 at the end oftheir execution (see FIGS. 11-12 and corresponding text for furtherdetails).

FIG. 11 is a diagram showing an L2 cache's state after executing testpatterns on a plurality of processors a first round. FIG. 11 is similarto FIG. 10 with the exception that processor A 1030 and processor B 1035have finished executing test pattern 0 1010 and test pattern 1 1015,respectively, for a first time.

After a first round of test pattern execution, L2 cache 1040 includesinformation in entries E0 1100 through E3 1130. Two lines “fit” intoentry 1100 during test pattern execution, which are X4 1070 (from testpattern 0 1010) and Y3 1074 (from test pattern 1 1015). As can be seen,at the end of the first test pattern execution round, Y3 1074 is pulledin first, and then X4 1070, which is why X4 1070 remains in entry 0 1100at the end of the execution. In other words, test pattern 0 1010's “loadX4” was executed after test pattern 1 1015's “store Y3.” This is due tothe fact that memory line fetching from main memory 1060 to L2 cache1040 takes few processor cycles, which results in instruction executionsequence changes across test patterns. In addition, as can be seen,entry 1 1110 includes X2 1064 information, entry 2 1120 includes Y21072's information, and entry 3 1130 includes information from both X11062 and Y1 1068. Therefore, during the next test pattern executionround, this information is not pulled from main memory 1060 because italready resides in L2 cache 1040, thus creating a different timingscenario.

FIG. 12 is a diagram showing an L2 cache's state after executing testpatterns on a plurality of processors a second round. FIG. 12 is similarto FIG. 11 with the exception that processor A 1030 and processor B 1035have executed test pattern 0 1010 and test pattern 1 1015, respectively,for a second time.

After the second round of test pattern execution, L2 cache 1040 includesinformation in entries E0 1100 through E3 1130. At the end of the secondround, however, Y3 1074 remains in E0 1100. This is due the fact thatduring the second test pattern execution round, X4 1070 is pulled in toentry E0 1100 first, and then Y3 1074. As a result, Y3 1074 remains inentry 0 1100 at the end of the second test pattern execution round, thuscreating a different timing scenario for a third execution round.

FIG. 13 is a diagram showing cache snoop logic and coherencyverification between an instruction cache (icache) and a data cache(dcache). In general, test patterns use different cache lines forinstructions and data even when they share the same page of memory. Assuch, a specific cache line may not reside in both instruction and datacaches at the same time. In order to test the L1 instruction and datalevel coherency, the invention described herein simultaneously uses thesame cache line as part of both icache 1350 and dcache 1360, both ofwhich reside within processor 1340.

Instruction stream 1300 includes instructions that correspond toparticular cache lines within L2 cache 1370, such as entry Y 1305, entryZ 1310, and entry X 1315. As can be seen, entry X 1315 corresponds tomultiple instruction lines due to the fact that each entry (cache line)is larger than a single instruction.

Instruction stream 1300 includes branch instruction 1320, which branchesto instruction 1330. By branching, instruction stream 1300 creates aninstruction stream “hole” in entry X 1315 between instruction 1320 andinstruction 1330. The instruction stream hole is an area within theinstruction stream that is not currently utilized due to a branchinstruction, which allows the invention described herein the ability tostore data in memory corresponding to the instruction stream hole(discussed below).

When processor 1340 begins executing instruction 1330, processor 1340pulls in the corresponding instruction line located in entry 1315 intoicache line 1355 (located in icache 1350). In order to completeinstruction 1330, processor 1340 also pulls in entry X 1315 into dcache1360 at dcache line 1365 because the instruction is to store data in alocation included in entry X 1315 (address 0X1024). Processor 1340executes instruction 1330, which requires changes to data line 1365since instruction 1330 targets an address location within the data line.However, data line 1365 is suppose to include the same information asicache line 1355 since they correspond to the same cache line. Whensnoop logic functions properly, the snoop logic identifies thediscrepancy between icache line 1355 and dcache line 1365 and, as aresult, icache 1350 invalidates icache line 1355 and retrieves a newupdated line that includes the changes made when executing instruction1330.

FIG. 14 is a diagram showing a processor executing multiple testpatterns that were generated in a manner to quickly test each entry in atranslation lookaside buffer (TLB). Test patterns are generated in orderto ensure that the test patterns cover an entire TLB region. During testpattern generation, new translations are created such that thetranslation corresponds to the next TLB entry in order for entire TLBcoverage until each entry in TLB 1450 is occupied (see FIG. 16 andcorresponding text for further details). As can be seen, when processor1400 invokes thread 0 1410 and thread 1 1430 to execute test pattern 01420 and test pattern 1 1440, respectively, entry 0 1455 and entry N1470 include translations corresponding to test pattern 0 1420 and entry1 1460 and entry 2 1465 include translations corresponding to testpattern 1 1440.

FIG. 15 is a diagram showing a processor executing multiple testpatterns on multiple threads to fully test an L2 cache. Processor 1500includes L2 cache 1550 that “holds” recently visited data andinstructions, and is “close” to processor 1500's core for performancepurposes. Typically, more than one unit (e.g., load/store unit, MMUetc.) accesses L2 cache 1550. In addition, threads usually share thesame on-chip cache, such as thread 0 1510 and thread 1 1530. As such, L2cache 1550 plays a crucial role in processor performance and, therefore,L2 cache 1550 verification is essential. The invention described hereinprovides an efficient way of testing each of L2 cache 1550's cachebyte/sector/word, as well as coherency, when more than one unit (MMU,processor, threads, etc.) compete for a cache line.

When more than one thread accesses a cache, the invention describedherein implements “false sharing” in order for two different threads toshare the same cache line, but different bytes/sectors/words within thesame cache line. Similarly, to stress the coherency and create a racecondition, page table memory and data memory are enabled for sharing sothat an MMU (for page table) and a processor (for data) access the samecache line at the same time.

During execution, test pattern 0 1520 accesses one unit of a cache line(byte/half word/word) and test pattern 1 1540 accesses a different unitof the same cache line. In other words, the test patterns share thecache line but not the same unit (byte/word/sector). In turn, more bytesare covered in a less amount of time since they are false shared. As canbe seen, entry 0 1555, entry 1 1560, and entry N 1570 includeinformation pertaining to both test pattern 0 1520 and test pattern 11540. Entry 1 1560 includes information corresponding to test pattern 11540.

In addition, coherency and race condition tests are performed. For thesetests, page table memory and data memory are shared between units.Therefore, both the MMU and the processor access the same cache linesimultaneously. For example, the MMU may access the cache line forupdating register/control bits and the processor may access the cacheline to update data.

The embodiment shown in FIG. 15 is an embodiment where L2 cache 1550 isnot shared between multiple processors. In another embodiment, however,multiple processors may share L2 cache 1550, which results in more testpatterns covering L2 cache 1550.

FIG. 16 is a flowchart showing steps taken in testing an entire TLBmemory. The invention described herein creates new translationscorresponding to unoccupied TLB entries until each entry is occupied inorder to provide full test coverage of the TLB. As those skilled in theart can appreciate, FIG. 16 represents building both data andinstruction translations.

Processing commences at 1600, whereupon processing randomly picks aninstruction from the set/pool of instructions defined by architecturaldetails for the processor to include in a test pattern (step 1610). Adetermination is made as to whether the instruction is a load/storeinstruction (decision 1620). If the unit is not a load/storeinstruction, decision 1620 branches to “No” branch 1622 whereuponprocessing builds the instruction at step 1660.

On the other hand, if the instruction is a load/store instruction,decision 1620 branches to “Yes” branch 1628 whereupon a determination ismade as to whether the TLB is full (decision 1630). If the TLB is full,signifying that the TLB is fully covered, decision 1630 branches to“Yes” branch 1632 whereupon processing selects any effective address andtranslation to build the load/store instruction at step 1635, and buildsthe instruction at step 1660.

On the other hand, if the TLB is not full, decision 1630 branches to“No” branch 1638 whereupon processing calls a memory manager to providean effective address for which a translation does not currently exist(step 1640). At step 1650, processing builds a new translation using theprovided address, which loads into the next empty TLB entry. At step1660, processing then builds the load/store instruction.

A determination is made as to whether to continue to create the testpattern (decision 1670). If processing should continue to create thetest pattern, decision 1670 branches to “Yes” branch 1672 which loopsback to randomly pick and process another instruction. This loopingcontinues until processing should terminate test pattern generation, atwhich point decision 1670 branches to “No” branch 1678 whereuponprocessing provides the test pattern to a test pattern executor (step1680), and processing ends at 1690.

FIG. 17 is a flowchart showing steps taken in providing full testcoverage of a cache. Processing commences at 1700, whereupon processingrandomly selects an instruction from a set/pool of instructions toinclude in a test pattern at step 1710. The set/pool of instructions aredefined based upon architectural details of a particular processor. Adetermination is made as to whether the instruction is a load/storeinstruction (decision 1720). If the instruction is not a load/storeinstruction, decision 1720 branches to “No” branch 1722 whereuponprocessing builds the instruction at step 1760.

On the other hand, if the instruction is a load/store instruction,decision 1720 branches to “Yes” branch 1728 whereupon processing calls amemory manager to provide an address for the load/store instruction(step 1730). A determination is made as to whether the byte/word/sectorcorresponding to the address is already used by another instruction(decision 1740). If the byte/word/sector is not already used, decision1740 branches to “No” branch 1742 whereupon processing builds theinstruction using the supplied address at step 1760.

On the other hand, if the byte is already used by another instruction,decision 1740 branches to “Yes” branch 1748 whereupon a determination ismade as to whether the cache is completely covered (decision 1750). Ifthe cache is not completely covered (bytes still empty), decision 1750branches to “No” branch 1752, which loops back to call the memorymanager to provide a different address. This looping continues until thecache is completely covered, at which point decision 1750 branches to“Yes” branch 1758 whereupon processing builds the instruction using theprovided address at step 1760.

A determination is made as to whether to continue test patterngeneration (decision 1770). If test pattern generation should continue,decision 1770 branches to “Yes” branch 1772, which loops back to selectand process another instruction. This looping continues until processingshould terminate test pattern generation, at which point decision 1770branches to “No” branch 1778 whereupon processing ends at 1780.

FIG. 18 is a flowchart showing steps taken in generating test patternsto test lwarx (Load Word And Reserve Index form) and stwcx (Store WordConditional) instructions. A lwarx instruction establishes a reservationon an address/granule, and a stwcx instruction targeted to the sameaddress/granule “succeeds” only if the reservation for the granule stillexists (conditional store). Since the reservation may be lost due tosituations such as, for example, a processor (or another processor)executing a another lwarx or ldarx (Load Double Word And Reserve Indexform) instruction, which clears the first reservation and establishes anew reservation, the invention described herein builds test patterns ina manner that ensures, stwcx success/failure predictability. As aresult, stwcx instructions are testable during test pattern execution(see FIG. 19 for further details).

Processing commences at 1800, whereupon processing randomly selects aninstruction from a set/pool of instructions to include in a test patternat step 1810. The set/pool of instructions are defined based uponarchitectural details of a particular processor. A determination is madeas to whether the selected instruction is a lwarx instruction (decision1820). A lwarx instruction creates a reservation in the processor foruse by a stwcx instruction. If a reservation exists and the storagelocation specified by the stwcx is the same as that specified by theLoad and Reserve instruction lwarx that established the reservation, thedata is stored at the address by the stwcx instruction and thereservation is cleared. Otherwise, the reservation is cleared and nostore is performed. If the selected instruction is a lwarx instruction,decision 1820 branches to “Yes” branch 1822 whereupon processing selectsa random address/granule that is not used by another store instructionfor the lwarx instruction (step 1825), and reserves the selectedaddress/granule for an upcoming paired stwcx instruction and marks itunusable by any other store instruction, other processor, or mechanism(step 1830).

On the other hand, if the selected instruction is not a lwarxinstruction, decision 1820 branches to “No” branch 1828 whereupon adetermination is made as to whether the selected instruction is a dcbainstruction, a dcbz instruction, or a dcbst instruction. A dcba (datacache block allocate) instruction, a dcbz (data cache block to zeros)instruction, and a dcbst (data cache block to main storage) instructionare all types of cache management instructions. If the selectedinstruction is a dcba instruction, a dcbz instruction, or a dcbstinstruction, decision 1840 branches to “Yes” branch 1842 whereuponprocessing identifies whether a paired lwarx-stwcx is in process ofbeing built and, if so, processing selects an address/granule other thanthe granule reserved by the lwarx instruction. If no paired lwarx-stwcxis being built, processing selects an address/granule withoutlimitations and builds the instruction (step 1845).

On the other hand, if the selected instruction is not a dcba, dcbz, ordcbst instruction, decision 1840 branches to “No” branch 1848 whereupona determination is made as to whether the selected instruction is astwcx instruction (decision 1850). If the selected instruction is not astwcx instruction, decision 1850 branches to “Yes” branch 1852 whereuponprocessing, if the stwcx is paired with a lwarx instruction, uses anaddress/granule reserved by the paired lwarx instruction. If the stwcxinstruction is not paired with a lwarx instruction, processing selects aunique address/granule for the stwcx instruction and builds theinstruction. On the other hand, if the selected instruction is not astwcx instruction, processing branches to “No” branch 1858 whereuponprocessing builds the selected instruction type.

A determination is made as to whether to continue to build the testpattern (decision 1870). If processing should continue to build the testpattern, decision 1870 branches to “Yes” branch 1872, which loops backto proceed to the next instruction (step 1875), and processes theinstruction. This looping continues until processing should stopgenerating the test pattern, at which point decision 1870 branches to“No” branch 1878, whereupon processing ends at 1880.

FIG. 19 is a diagram showing test pattern execution that includes pairedlwarx-stwcx instructions in a non-interrupt mode. In non-interrupt mode,stwcx failures are tested as well as stwcx successes. Since a stwcxinstruction succeeds when a reservation exists for the particulargranule reserved by a previous lwarx instruction, two scenarios exist inwhich stwcx success is predictable.

The first scenario is a “success case.” A success case is when a stwcxinstruction is built to succeed and has to be predicted forsuccess/fail. In a multi-core system, difficulty arises when controllingother processors to access the same granule. To achieve this, the stwcxinstruction is built such that it matches a previous lwarxaddress/granule. Other processors' test patterns are built in such a waythat other processors cannot access that reserved granule. As a result,the granule is reserved for a particular core. In addition, no otherinstructions (stores, dcba, dcbst, etc.) are built in between alwarx-stwcx instruction pair and, therefore, the stwcx instruction isbuilt to succeed. Since the system is in a non-interrupt mode, nocontext switch occurs while executing the test pattern. Therefore, thestwcx instruction succeeds because the reservation is not lost. As such,the result is predictable.

The second scenario is a “failure case” when a stwcx instruction isdesigned to always fail, which still results in a predictable scenario.In order to achieve this predictable scenario, the stwcx instructionalways executes on a different address/granule other than that of thepaired lwarx instruction that established the reservation.

Test pattern 1900 includes instructions 1910 through 1930. Instructions1910 and 1920 are paired with each other (first scenario), whileinstruction 1930 is not paired with any lwarx instruction (secondscenario). As test pattern 1900 executes instruction 1910, instruction1910 reserves location X 1950 in main memory 1940 for paired stwcxinstruction 1920. As such, instruction 1920 performs a successful storeinto location X 1950. In contrast, instruction 1930 is not able to storeinformation into location Y 1960 because it is not previously reservedby a paired lwarx instruction.

FIG. 20 is a table showing different test pattern execution scenariosthat result in different bus contention scenarios. In a multi-processorscenario, processors share a front side bus and all transactions to thememory flow on the bus in which a bus arbiter determines the bus owner.As a result, bus contention exists. An arbitration algorithm, however,improves the performance of the bus. The invention described hereinprovides a method to stress the bus with different timings in a shortertimeframe by providing different memory accesses in a different order byinfluencing different cache state and TLB states using the same testpatterns. By creating multiple test patterns for a multi-processorsystem, and repeatedly executing the test patterns without rebuildingthe test patterns, enables a system to spend more time testing the busand other functional units in the processor (e.g., fixed and floatingpoint units, VMX units, load/store units, etc.) rather than buildingtest patterns.

Table 2000 includes columns 2010 through 2040 and rows 2050 through2080. Each of rows 2050 through 2080 represent a test pattern to executeon a first processor (processor A 2045), and each of columns 2010through 2040 represent a test pattern to execute on a second processor(processor B 2005). The example shown in FIG. 1 shows that four testpatterns are created (test patterns A, B, C, and D), which access thesame memory and cache lines. As one skilled in the art can appreciate,more or less test patterns may be created than what is represented inFIG. 20.

Since each test pattern accesses the same memory and cache lines, thecache and TLB states are different at any given state based upon thetest pattern sequence. Therefore, by creating different test patternsequences, different start caches result and, therefore, different bustimings result.

For example, when test pattern B is executed on processor A 2045 (row2060) and test pattern D is executed on processor B 2005 (column 2040),the row/column intersection shows that the TLB, L1, L2 and bus statescorrespond to a “B,D” state. In another example, when test pattern A isexecuted on processor A (row 2050) and test pattern C is executed onprocessor B (column 2030), the row/column intersection shows that theTLB, L1, L2 and bus states correspond to an “A,C” state. In short, byexecuting the same test patterns in a different order, different cacheand TLB states result (i.e. different bus contentions), which aretested.

FIG. 21 is a diagram showing two processors executing two different testpatterns, which results in a particular bus timing scenario anddifferent states of functional units during execution. Processor A 2100executes test pattern X 2110 and processor B 2140 executes test patternY 2150. As such, TLB 2115, SLB 2120, L1 2125, L2 2130, TLB 2155, SLB2160, L1 2165, L2 2170, and bus 2175 are in an “X, Y” state. When testpattern X 2110 executes on processor B 2140 and test pattern Y 2150executes on processor A 2100, the states of the TLB's, SLB's, L1's, L2'sand bus 2175 change to “Y, X.” As can be seen, different test patterncombinations on two processors create different timing and statescenarios on the processor units and bus. As a result, the inventiondescribed herein allows processor logic and bus testing using a limitedset of test patterns in a shorter time since numerous test patterns arenot required to be built.

FIG. 22 is a diagram showing a broadband element architecture whichincludes a plurality of heterogeneous processors capable of implementingthe invention described herein. The heterogeneous processors share acommon memory and a common bus. Broadband element architecture (BEA)2200 sends and receives information to/from external devices throughinput output 2270, and distributes the information to control plane 2210and data plane 2240 using processor element bus 2260. Control plane 2210manages BEA 2200 and distributes work to data plane 2240.

Control plane 2210 includes processing unit 2220 which runs operatingsystem (OS) 2225. For example, processing unit 2220 may be a Power PCcore that is embedded in BEA 2200 and OS 2225 may be a Linux operatingsystem. Processing unit 2220 manages a common memory map table for BEA2200. The memory map table corresponds to memory locations included inBEA 2200, such as L2 memory 2230 as well as non-private memory includedin data plane 2240.

Data plane 2240 includes Synergistic processing element's (SPE) 2245,2250, and 2255. Each SPE is used to process data information and eachSPE may have different instruction sets. For example, BEA 2200 may beused in a wireless communications system and each SPE may be responsiblefor separate processing tasks, such as modulation, chip rate processing,encoding, and network interfacing. In another example, each SPE may haveidentical instruction sets and may be used in parallel to performoperations benefiting from parallel processes. Each SPE includes asynergistic processing unit (SPU) which is a processing core, such as adigital signal processor, a microcontroller, a microprocessor, or acombination of these cores.

SPE 2245, 2250, and 2255 are connected to processor element bus 2260,which passes information between control plane 2210, data plane 2240,and input/output 2270. Bus 2260 is an on-chip coherent multi-processorbus that passes information between I/O 2270, control plane 2210, anddata plane 2240. Input/output 2270 includes flexible input-output logicwhich dynamically assigns interface pins to input output controllersbased upon peripheral devices that are connected to BEA 2200.

FIG. 23 is a block diagram illustrating a processing element having amain processor and a plurality of secondary processors sharing a systemmemory. Broadband Element Architecture (BEA) 2305 includes processingunit (PU) 2310, which, in one embodiment, acts as the main processor andruns the operating system. Processing unit 2310 may be, for example, aPower PC core executing a Linux operating system. BEA 2305 also includesa plurality of synergistic processing elements (SPEs) such as SPEs 2345through 2385. Each SPE includes a synergistic processing unit (SPU) thatact as secondary processing units to PU 2310, a memory storage unit, andlocal storage. For example, SPE 2345 includes SPU 2360, MMU 2355, andlocal storage 2359; SPE 2365 includes SPU 2370, MMU 2375, and localstorage 2379; and SPE 2385 includes SPU 2390, MMU 2395, and localstorage 2399.

In one embodiment, the SPEs process data under the control of PU 2310.The SPEs may be, for example, digital signal processing cores,microprocessor cores, micro controller cores, etc., or a combination ofthe above cores. In one embodiment, each one of the local stores is astorage area associated with a particular SPU. Each SPU can configureits local store as a private storage area, a shared storage area, or anSPU's local store may be partly private and partly shared.

For example, if an SPU requires a substantial amount of local memory,the SPU may allocate 100% of its local store to private memoryaccessible only by that SPU. If, on the other hand, an SPU requires aminimal amount of local memory, the SPU may allocate 10% of its localstore to private memory and the remaining 90% to shared memory. Theshared memory is accessible by PU 2310 and by the other SPEs. An SPU mayreserve part of its local store in order for the SPU to have fast,guaranteed access to some memory when performing tasks that require suchfast access. The SPU may also reserve some of its local store as privatewhen processing sensitive data, as is the case, for example, when theSPU is performing encryption/decryption.

The MMUs are responsible for transferring data between an SPU's localstore and the system memory. In one embodiment, an MMU includes a directmemory access (DMA) controller configured to perform this function.

Each SPE may be set up to perform a different task, and accordingly, inone embodiment, each SPE may be accessed using different instructionsets. If BEA 2305 is being used in a wireless communications system, forexample, each SPE may be responsible for separate processing tasks, suchas modulation, chip rate processing, encoding, network interfacing, etc.In another embodiment, each SPE may have identical instruction sets andmay be used in parallel to perform operations benefiting from parallelprocesses.

The shared portion of the SPEs' local stores may be accessed by PU 2310as well as by the other SPEs by mapping each shared region to systemmemory 2320. In one embodiment, PU 2310 manages the memory map for thecommon system memory 2320. The memory map table may include PU 2310's L2Cache 2315, system memory 2320, as well as the SPEs' shared localstores.

A portion of system memory 2320 as shown is occupied by the operatingsystem (OS 2325). System Memory 2325 also contains data 2340, whichrepresents data to be processed by SPU 2310 as well as by the SPEs. Inone embodiment, a process executing on the PU receives a request for atask involving the processing of large data. The PU first determines anoptimum method for performing the task as well as an optimum placementof the data in common system memory 2320. The PU may then initiate atransfer of the data to be processed from disk 2335 to system memory2320. In one embodiment, the PU arranges the data in system memory 2325in data blocks the size of the registers of the SPEs. In one embodiment,the SPEs may have 128 registers, each register being 128 bits long.

The PU then searches for available SPEs and assigns blocks of data toany available SPEs for processing of the data. The SPEs can access thecommon system memory (through a DMA command, for example) transfer thedata to the SPEs' local store, and perform the assigned operations.After processing the data, the SPEs may transfer the data (using DMAagain, for example) back to common system memory 2320. This proceduremay be repeated as SPEs become available until all the data blocks havebeen processed.

FIG. 24 illustrates information handling system 2401 which is asimplified example of a computer system capable of performing thecomputing operations described herein. Computer system 2401 includesprocessor 2400 which is coupled to host bus 2402. A level two (L2) cachememory 2404 is also coupled to host bus 2402. Host-to-PCI bridge 2406 iscoupled to main memory 2408, includes cache memory and main memorycontrol functions, and provides bus control to handle transfers amongPCI bus 2410, processor 2400, L2 cache 2404, main memory 2408, and hostbus 2402. Main memory 2408 is coupled to Host-to-PCI bridge 2406 as wellas host bus 2402. Devices used solely by host processor(s) 2400, such asLAN card 2430, are coupled to PCI bus 2410. Service Processor Interfaceand ISA Access Pass-through 2412 provides an interface between PCI bus2410 and PCI bus 2414. In this manner, PCI bus 2414 is insulated fromPCI bus 2410. Devices, such as flash memory 2418, are coupled to PCI bus2414. In one implementation, flash memory 2418 includes BIOS code thatincorporates the necessary processor executable code for a variety oflow-level system functions and system boot functions.

PCI bus 2414 provides an interface for a variety of devices that areshared by host processor(s) 2400 and Service Processor 2416 including,for example, flash memory 2418. PCI-to-ISA bridge 2435 provides buscontrol to handle transfers between PCI bus 2414 and ISA bus 2440,universal serial bus (USB) functionality 2445, power managementfunctionality 2455, and can include other functional elements not shown,such as a real-time clock (RTC), DMA control, interrupt support, andsystem management bus support. Nonvolatile RAM 2420 is attached to ISABus 2440. Service Processor 2416 includes JTAG and I2C busses 2422 forcommunication with processor(s) 2400 during initialization steps.JTAG/I2C busses 2422 are also coupled to L2 cache 2404, Host-to-PCIbridge 2406, and main memory 2408 providing a communications pathbetween the processor, the Service Processor, the L2 cache, theHost-to-PCI bridge, and the main memory. Service Processor 2416 also hasaccess to system power resources for powering down information handlingdevice 2401.

Peripheral devices and input/output (I/O) devices can be attached tovarious interfaces (e.g., parallel interface 2462, serial interface2464, keyboard interface 2468, and mouse interface 2470 coupled to ISAbus 2440. Alternatively, many I/O devices can be accommodated by a superI/O controller (not shown) attached to ISA bus 2440.

In order to attach computer system 2401 to another computer system tocopy files over a network, LAN card 2430 is coupled to PCI bus 2410.Similarly, to connect computer system 2401 to an ISP to connect to theInternet using a telephone line connection, modem 2475 is connected toserial port 2464 and PCI-to-ISA Bridge 2435.

While FIG. 24 shows one information handling system that employsprocessor(s) 2400, the information handling system may take many forms.For example, information handling system 2401 may take the form of adesktop, server, portable, laptop, notebook, or other form factorcomputer or data processing system. Information handling system 2401 mayalso take other form factors such as a personal digital assistant (PDA),a gaming device, ATM machine, a portable telephone device, acommunication device or other devices that include a processor andmemory.

One of the preferred implementations of the invention is a clientapplication, namely, a set of instructions (program code) in a codemodule that may, for example, be resident in the random access memory ofthe computer. Until required by the computer, the set of instructionsmay be stored in another computer memory, for example, in a hard diskdrive, or in a removable memory such as an optical disk (for eventualuse in a CD ROM) or floppy disk (for eventual use in a floppy diskdrive), or downloaded via the Internet or other computer network. Thus,the present invention may be implemented as a computer program productfor use in a computer. In addition, although the various methodsdescribed are conveniently implemented in a general purpose computerselectively activated or reconfigured by software, one of ordinary skillin the art would also recognize that such methods may be carried out inhardware, in firmware, or in more specialized apparatus constructed toperform the required method steps.

While particular embodiments of the present invention have been shownand described, it will be obvious to those skilled in the art that,based upon the teachings herein, that changes and modifications may bemade without departing from this invention and its broader aspects.Therefore, the appended claims are to encompass within their scope allsuch changes and modifications as are within the true spirit and scopeof this invention. Furthermore, it is to be understood that theinvention is solely defined by the appended claims. It will beunderstood by those with skill in the art that if a specific number ofan introduced claim element is intended, such intent will be explicitlyrecited in the claim, and in the absence of such recitation no suchlimitation is present. For non-limiting example, as an aid tounderstanding, the following appended claims contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimelements. However, the use of such phrases should not be construed toimply that the introduction of a claim element by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim element to inventions containing only one such element,even when the same claim includes the introductory phrases “one or more”or “at least one” and indefinite articles such as “a” or “an”; the sameholds true for the use in the claims of definite articles.

1. A computer-implemented method comprising: simultaneously executing afirst test pattern on a first processor and a second test pattern on asecond processor, resulting in a first test pattern execution round;after the first test pattern execution round, computing a first hardwareregister error detection check value; comparing the first hardwareregister error detection check value to a simulation register errordetection check value; after the comparing, simultaneously re-executingthe first test pattern on the first processor and re-executing thesecond test pattern on the second processor, resulting in a second testpattern execution round; after the second test pattern execution round,computing a second hardware register error detection check value;comparing the second hardware register error detection check value tothe simulation register error detection check value; and setting anerror flag if the first hardware register error detection check value orthe second hardware register error detection check value do not matchthe simulation register error detection check value based upon thecomparison.
 2. The method of claim 1 wherein, after the first testpattern execution round, data corresponding to the first test patternresides in a first cache line, and after the second test patternexecution round, data from the second pattern resides in the first cacheline.
 3. The method of claim 1 wherein the first execution round and thesecond execution round commence at a different initial cache memorystate, and wherein the first hardware register error detection checkvalue equals the second hardware register error detection check value.4. The method of claim 1 wherein the executing is performed using afalse sharing mode, and wherein the first cache line includesinformation corresponding to the first test pattern and also includesinformation corresponding to the second test pattern.
 5. The method ofclaim 4 wherein the information corresponding to the first test patternis data and the information corresponding to the second test pattern isinstruction.
 6. The method of claim 1 further comprising: in response tothe error flag not being set, computing a hardware memory errordetection check value; comparing the hardware memory error detectioncheck value with a simulation memory error detection check value; and inresponse to the comparing, setting the error flag if the hardware memoryerror detection check value does not match the simulation memory errordetection check value.
 7. An information handling system comprising: oneor more processors; a memory accessible by the processors; one or morenonvolatile storage devices accessible by the processors; and a set ofinstructions stored in the memory, wherein one or more of the processorsexecutes the set of instructions in order to perform actions of:simultaneously executing a first test pattern on a first processor and asecond test pattern on a second processor, resulting in a first testpattern execution round; after the first test pattern execution round,computing a first hardware register error detection check value;comparing the first hardware register error detection check value to asimulation register error detection check value; after the comparing,simultaneously re-executing the first test pattern on the firstprocessor and re-executing the second test pattern on the secondprocessor, resulting in a second test pattern execution round; after thesecond test pattern execution round, computing a second hardwareregister error detection check value; comparing the second hardwareregister error detection check value to the simulation register errordetection check value; and setting an error flag if the first hardwareregister error detection check value or the second hardware registererror detection check value do not match the simulation register errordetection check value based upon the comparison.
 8. The informationhandling system of claim 7 wherein, after the first test patternexecution round, data corresponding to the first test pattern resides ina first cache line, and after the second test pattern execution round,data from the second pattern resides in the first cache line.
 9. Theinformation handling system of claim 7 wherein the first execution roundand the second execution round commence at a different initial cachememory state, and wherein the first hardware register error detectioncheck value equals the second hardware register error detection checkvalue.
 10. The information handling system of claim 7 wherein theexecuting is performed using a false sharing mode, and wherein the firstcache line includes information corresponding to the first test patternand also includes information corresponding to the second test pattern.11. The information handling system of claim 10 wherein the informationcorresponding to the first test pattern is data and the informationcorresponding to the second test pattern is instruction.
 12. Theinformation handling system of claim 7 further comprising an additionalset of instructions in order to perform actions of: in response to theerror flag not being set, computing a hardware memory error detectioncheck value; comparing the hardware memory error detection check valuewith a simulation memory error detection check value; and in response tothe comparing, setting the error flag if the hardware memory errordetection check value does not match the simulation memory errordetection check value.
 13. A computer program product stored on acomputer operable media, the computer operable media containinginstructions for execution by a computer, which, when executed by thecomputer, cause the computer to implement a method of processing testpatterns, the method comprising: simultaneously executing a first testpattern on a first processor and a second test pattern on a secondprocessor, resulting in a first test pattern execution round; after thefirst test pattern execution round, computing a first hardware registererror detection check value; comparing the first hardware register errordetection check value to a simulation register error detection checkvalue; after the comparing, simultaneously re-executing the first testpattern on the first processor and re-executing the second test patternon the second processor, resulting in a second test pattern executionround; after the second test pattern execution round, computing a secondhardware register error detection check value; comparing the secondhardware register error detection check value to the simulation registererror detection check value; and setting an error flag if the firsthardware register error detection check value or the second hardwareregister error detection check value do not match the simulationregister error detection check value based upon the comparison.
 14. Thecomputer program product of claim 13 wherein, after the first testpattern execution round, data corresponding to the first test patternresides in a first cache line, and after the second test patternexecution round, data from the second pattern resides in the first cacheline.
 15. The computer program product of claim 13 wherein the firstexecution round and the second execution round commence at a differentinitial cache memory state, and wherein the first hardware registererror detection check value equals the second hardware register errordetection check value.
 16. The computer program product of claim 13wherein the executing is performed using a false sharing mode, andwherein the first cache line includes information corresponding to thefirst test pattern and also includes information corresponding to thesecond test pattern.
 17. The computer program product of claim 16wherein the information corresponding to the first test pattern is dataand the information corresponding to the second test pattern isinstruction.
 18. The computer program product of claim 13 wherein themethod further comprises: in response to the error flag not being set,computing a hardware memory error detection check value; comparing thehardware memory error detection check value with a simulation memoryerror detection check value; and in response to the comparing, settingthe error flag if the hardware memory error detection check value doesnot match the simulation memory error detection check value.